Update purging limits #32
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We faced the same issue recently and when we've been reaching the limit of 2000 purges we still been able to purge more and more w/o any problems. Hence the actual limit is more than 2000. |
|
I have this patch successfully applied using our Drupal composer.json, it works nicely. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cloudflare's API supports up to 30,000 cache tag purges in a day (I think).
This is a bit unclear from Cloudflare's documentation, but they state that:
I'm guessing that 30,000 is the new limit, and 2,000 was the limit they had in place while they were rolling this feature out, but it would be great to confirm that.